UCI transmission for overlapping uplink resource assignments with repetition

ABSTRACT

Certain aspects of the present disclosure provide techniques for uplink control information (UCI) transmission for overlapping physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH) resource assignments with repetition. A method of wireless communication by a user equipment (UE) is provided. The method generally includes receiving scheduling to transmit on the PUSCH in a first one or more slots associated with a first number of repetitions and scheduling to transmit on the PUCCH in a second one or more slots associated with a second number of repetitions. The scheduled transmissions overlap in at least one slot. The method includes determining which channel to transmit UCI on and which channel to drop for each of the first and second one or more slots. The method includes transmitting or dropping the UCI in the first and second one or more slots in accordance with the determination.

CROSS-REFERENCE TO RELATED APPLICATION & PRIORITY CLAIM

This application is a continuation of U.S. application Ser. No.16/250,542, filed Jan. 17, 2019, which claims benefit of and priority toU.S. Provisional Patent Application Ser. No. 62/619,709, filed Jan. 19,2018, U.S. Provisional Patent Application Ser. No. 62/710,441, filedFeb. 16, 2018, and U.S. Provisional Patent Application Ser. No.62/634,797, filed Feb. 23, 2018, which are all herein incorporated byreference in their entireties as if fully set forth below and for allapplicable purposes.

BACKGROUND Field of the Disclosure

Aspects of the present disclosure relate to wireless communications andto techniques for uplink control information (UCI) transmission foroverlapping uplink resource assignments, such as physical uplink sharedchannel (PUSCH) and physical uplink control channel (PUCCH), withrepetition in certain systems such as in new radio (NR) systems.

Description of Related Art

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,broadcasts, etc. These wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, etc.). Examples of such multiple-access systems include3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE)systems, LTE Advanced (LTE-A) systems, code division multiple access(CDMA) systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, orthogonal frequency divisionmultiple access (OFDMA) systems, single-carrier frequency divisionmultiple access (SC-FDMA) systems, and time division synchronous codedivision multiple access (TD-SCDMA) systems, to name a few.

In some examples, a wireless multiple-access communication system mayinclude a number of base stations (BSs), which are each capable ofsimultaneously supporting communication for multiple communicationdevices, otherwise known as user equipments (UEs). In an LTE or LTE-Anetwork, a set of one or more base stations may define an eNodeB (eNB).In other examples (e.g., in a next generation, a new radio (NR), or 5Gnetwork), a wireless multiple access communication system may include anumber of distributed units (DUs) (e.g., edge units (EUs), edge nodes(ENs), radio heads (RHs), smart radio heads (SRHs), transmissionreception points (TRPs), etc.) in communication with a number of centralunits (CUs) (e.g., central nodes (CNs), access node controllers (ANCs),etc.), where a set of one or more DUs, in communication with a CU, maydefine an access node (e.g., which may be referred to as a BS, 5G NB,next generation NodeB (gNB or gNodeB), transmission reception point(TRP), etc.). A BS or DU may communicate with a set of UEs on downlinkchannels (e.g., for transmissions from a BS or DU to a UE) and uplinkchannels (e.g., for transmissions from a UE to BS or DU).

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. NR (e.g., new radio or 5G) is anexample of an emerging telecommunication standard. NR is a set ofenhancements to the LTE mobile standard promulgated by 3GPP. NR isdesigned to better support mobile broadband Internet access by improvingspectral efficiency, lowering costs, improving services, making use ofnew spectrum, and better integrating with other open standards usingOFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink(UL). To these ends, NR supports beamforming, multiple-inputmultiple-output (MIMO) antenna technology, and carrier aggregation.

However, as the demand for mobile broadband access continues toincrease, there exists a need for further improvements in NR and LTEtechnology. Preferably, these improvements should be applicable to othermulti-access technologies and the telecommunication standards thatemploy these technologies.

SUMMARY

The systems, methods, and devices of the disclosure each have severalaspects, no single one of which is solely responsible for its desirableattributes. Without limiting the scope of this disclosure as expressedby the claims which follow, some features will now be discussed briefly.After considering this discussion, and particularly after reading thesection entitled “Detailed Description” one will understand how thefeatures of this disclosure provide advantages that include improvedcommunications between access points and stations in a wireless network.

Certain aspects of the present disclosure generally relate to methodsand apparatus for uplink control information (UCI) transmission foroverlapping uplink resource assignments, such as for physical uplinkshared channel (PUSCH) and physical uplink control channel (PUCCH)resource assignments, with repetition in certain systems, such as newradio (NR) systems.

Certain aspects of the present disclosure provide a method for wirelesscommunication that may be performed, for example, by a user equipment(UE). The method generally includes receiving scheduling to transmit ona PUSCH in a first one or more slots associated with a first number ofrepetitions and scheduling to transmit on a PUCCH in a second one ormore slots associated with a second number of repetitions. The scheduledPUSCH and PUCCH transmissions overlap in at least one slot. The methodincludes determining to transmit UCI on the PUSCH and drop the scheduledPUCCH transmission, to transmit the UCI on the PUCCH and drop thescheduled PUSCH transmission, or to drop the UCI transmission for eachof the first and second one or more slots. The method includestransmitting or dropping the UCI in the first and second one or moreslots in accordance with the determination

Certain aspects of the present disclosure provide an apparatus forwireless communication such as a UE. The apparatus generally includesmeans for receiving scheduling to transmit on a PUSCH in a first one ormore slots associated with a first number of repetitions and schedulingto transmit on a PUCCH in a second one or more slots associated with asecond number of repetitions. The scheduled PUSCH and PUCCHtransmissions overlap in at least one slot. The apparatus includes meansfor determining to transmit UCI on the PUSCH and drop the scheduledPUCCH transmission, to transmit the UCI on the PUCCH and drop thescheduled PUSCH transmission, or to drop the UCI transmission for eachof the first and second one or more slots. The apparatus includes meansfor transmitting or dropping the UCI in the first and second one or moreslots in accordance with the determination

Certain aspects of the present disclosure provide an apparatus forwireless communication such as a UE. The apparatus generally includes areceiver configured to receive scheduling to transmit on a PUSCH in afirst one or more slots associated with a first number of repetitionsand scheduling to transmit on a PUCCH in a second one or more slotsassociated with a second number of repetitions. The scheduled PUSCH andPUCCH transmissions overlap in at least one slot. The apparatus includesat least one processor coupled with a memory and configured to determineto transmit UCI on the PUSCH and drop the scheduled PUCCH transmission,to transmit the UCI on the PUCCH and drop the scheduled PUSCHtransmission, or to drop the UCI transmission for each of the first andsecond one or more slots. The apparatus includes a transmitterconfigured to transmit or drop the UCI in the first and second one ormore slots in accordance with the determination

Certain aspects of the present disclosure provide a computer readablemedium having computer executable code stored thereon for wirelesscommunication by a UE. The computer executable code generally includescode for receiving scheduling to transmit on a PUSCH in a first one ormore slots associated with a first number of repetitions and schedulingto transmit on a PUCCH in a second one or more slots associated with asecond number of repetitions. The scheduled PUSCH and PUCCHtransmissions overlap in at least one slot. The computer executable codegenerally includes code for determining to transmit UCI on the PUSCH anddrop the scheduled PUCCH transmission, to transmit the UCI on the PUCCHand drop the scheduled PUSCH transmission, or to drop the UCItransmission for each of the first and second one or more slots. Thecomputer executable code generally includes code for transmitting ordropping the UCI in the first and second one or more slots in accordancewith the determination.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe appended drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above-recited features of the presentdisclosure can be understood in detail, a more particular description,briefly summarized above, may be had by reference to aspects, some ofwhich are illustrated in the drawings. It is to be noted, however, thatthe appended drawings illustrate only certain typical aspects of thisdisclosure and are therefore not to be considered limiting of its scope,for the description may admit to other equally effective aspects.

FIG. 1 is a block diagram conceptually illustrating an exampletelecommunications system, in accordance with certain aspects of thepresent disclosure.

FIG. 2 is a block diagram illustrating an example logical architectureof a distributed radio access network (RAN), in accordance with certainaspects of the present disclosure.

FIG. 3 is a diagram illustrating an example physical architecture of adistributed RAN, in accordance with certain aspects of the presentdisclosure.

FIG. 4 is a block diagram conceptually illustrating a design of anexample base station (BS) and user equipment (UE), in accordance withcertain aspects of the present disclosure.

FIG. 5 is a diagram showing examples for implementing a communicationprotocol stack, in accordance with certain aspects of the presentdisclosure.

FIG. 6 illustrates an example of a frame format for a new radio (NR)system, in accordance with certain aspects of the present disclosure.

FIG. 7 is a flow diagram illustrating example operations that may beperformed by a UE for uplink control information (UCI) transmission, inaccordance with certain aspects of the present disclosure.

FIG. 8 is a flow diagram illustrating example operations that may beperformed by a BS, in accordance with certain aspects of the presentdisclosure.

FIG. 9 illustrates a communications device that may include variouscomponents configured to perform operations for the techniques disclosedherein in accordance with aspects of the present disclosure.

FIG. 10 illustrates a communications device that may include variouscomponents configured to perform operations for the techniques disclosedherein in accordance with aspects of the present disclosure.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures. It is contemplated that elements disclosed in one aspectmay be beneficially utilized on other aspects without specificrecitation.

DETAILED DESCRIPTION

Aspects of the present disclosure provide apparatus, methods, processingsystems, and computer readable mediums for NR (new radio accesstechnology or 5G technology). NR may support various wirelesscommunication services, such as enhanced mobile broadband (eMBB)targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW)targeting high carrier frequency (e.g. 25 GHz or beyond), massivemachine type communications (mMTC) targeting non-backward compatible MTCtechniques, and/or mission critical targeting ultra-reliable low-latencycommunications (URLLC). These services may include latency andreliability requirements. These services may also have differenttransmission time intervals (TTI) to meet respective quality of service(QoS) requirements. In addition, these services may co-exist in the samesubframe.

In certain systems, such as NR, channels such as the physical uplinkshared channel (PUSCH) and physical uplink control channel (PUCCH) canbe configured for repetitions. Transmission of uplink controlinformation (UCI) in these channels may be based on rules. Based on therules, the user equipment (UE) can transmit the UCI in the PUCCH,piggyback the UCI in the PUSCH, or drop the UCI or a portion of the UCI.In some cases, the rules are defined for determining the UCItransmission for the case of no repetition (e.g., repetition factor=1);however, because in NR the PUSCH and PUCCH can be configured forrepetitions (e.g., repetition factor=2, 4, 8, etc.), techniques forapplying UCI rules for the case of repetitions are desirable.

Accordingly, aspects of the present disclosure provide techniques andapparatus for UCI transmission for overlapping PUSCH and PUCCH resourceassignments with repetitions.

The following description provides examples, and is not limiting of thescope, applicability, or examples set forth in the claims. Changes maybe made in the function and arrangement of elements discussed withoutdeparting from the scope of the disclosure. Various examples may omit,substitute, or add various procedures or components as appropriate. Forinstance, the methods described may be performed in an order differentfrom that described, and various steps may be added, omitted, orcombined. Also, features described with respect to some examples may becombined in some other examples. For example, an apparatus may beimplemented or a method may be practiced using any number of the aspectsset forth herein. In addition, the scope of the disclosure is intendedto cover such an apparatus or method which is practiced using otherstructure, functionality, or structure and functionality in addition to,or other than, the various aspects of the disclosure set forth herein.It should be understood that any aspect of the disclosure disclosedherein may be embodied by one or more elements of a claim. The word“exemplary” is used herein to mean “serving as an example, instance, orillustration.” Any aspect described herein as “exemplary” is notnecessarily to be construed as preferred or advantageous over otheraspects.

The techniques described herein may be used for various wirelesscommunication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA,SC-FDMA and other networks. The terms “network” and “system” are oftenused interchangeably. A CDMA network may implement a radio technologysuch as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRAincludes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implementa radio technology such as Global System for Mobile Communications(GSM). An OFDMA network may implement a radio technology such as NR(e.g. 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRAand E-UTRA are part of Universal Mobile Telecommunication System (UMTS).

New Radio (NR) is an emerging wireless communications technology underdevelopment in conjunction with the 5G Technology Forum (5GTF). 3GPPLong Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTSthat use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described indocuments from an organization named “3rd Generation PartnershipProject” (3GPP). cdma2000 and UMB are described in documents from anorganization named “3rd Generation Partnership Project 2” (3GPP2). Thetechniques described herein may be used for the wireless networks andradio technologies mentioned above as well as other wireless networksand radio technologies. For clarity, while aspects may be describedherein using terminology commonly associated with 3G and/or 4G wirelesstechnologies, aspects of the present disclosure can be applied in othergeneration-based communication systems, such as 5G and later, includingNR technologies.

Example Wireless Communications System

FIG. 1 illustrates an example wireless communication network 100 inwhich aspects of the present disclosure may be performed. For example,the wireless network 100 may be a new radio (NR) or 5G network. A UE 120in the wireless communication network 100 may be configured to receivescheduling for physical uplink shared channel (PUSCH) transmission andscheduling for physical uplink control channel (PUCCH) transmission, forexample, from a BS 110 in the wireless communication network 100. ThePUSCH and PUCCH may be scheduled for repetitions. The UE 120 may bescheduled to transmit PUSCH and PUCCH in overlapping slots in a subframeand/or in overlapping orthogonal frequency division multiplexing (OFDM)symbols within a slot. The UE 120 may have uplink control information(UCI) to send and may determine whether to drop the UCI, drop the PUCCHand piggyback the UCI on the PUSCH, or transmit the UCI on the PUCCH anddrop the PUSCH. The UE 120 may make the determination based on rulesdescribed in more detail below. The UE 120 rules may apply to a singlerepetition or be applied to multiple or all slots in a resourceassignment. The rules may be based on a plurality of factors including,but not limited to, the nature of scheduled overlap, a priority ofchannel, logical channels, and/or information associated with thechannel and logical channels, content of the transmissions, the resourceassignments associated with the scheduling, and/or other factors.

As illustrated in FIG. 1, the wireless communication network 100 mayinclude a number of base stations (BSs) 110 and other network entities.A BS may be a station that communicates with user equipments (UEs). EachBS 110 may provide communication coverage for a particular geographicarea. In 3GPP, the term “cell” can refer to a coverage area of a Node B(NB) and/or a NB subsystem serving this coverage area, depending on thecontext in which the term is used. In NR systems, the term “cell” andnext generation NodeB (gNB or gNodeB), access point (AP), ortransmission reception point (TRP) may be interchangeable. In someexamples, a cell may not necessarily be stationary, and the geographicarea of the cell may move according to the location of a mobile BS. Insome examples, the base stations may be interconnected to one anotherand/or to one or more other base stations or network nodes (not shown)in wireless communication network 100 through various types of backhaulinterfaces, such as a direct physical connection, a wireless connection,a virtual network, or the like using any suitable transport network.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular radioaccess technology (RAT) and may operate on one or more frequencies. ARAT may also be referred to as a radio technology, an air interface,etc. A frequency may also be referred to as a carrier, a subcarrier, afrequency channel, a tone, a subband, etc. Each frequency may support asingle RAT in a given geographic area in order to avoid interferencebetween wireless networks of different RATs. In some cases, NR or 5G RATnetworks may be deployed.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or other types of cells. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having an association with the femto cell(e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in thehome, etc.). A BS for a macro cell may be referred to as a macro BS. ABS for a pico cell may be referred to as a pico BS. A BS for a femtocell may be referred to as a femto BS or a home BS. In the example shownin FIG. 1, the BSs 110 a, 110 b and 110 c may be macro BSs for the macrocells 102 a, 102 b and 102 c, respectively. The BS 110 x may be a picoBS for a pico cell 102 x. The BSs 110 y and 110 z may be femto BSs forthe femto cells 102 y and 102 z, respectively. ABS may support one ormultiple (e.g., three) cells.

Wireless communication network 100 may also include relay stations. Arelay station is a station that receives a transmission of data and/orother information from an upstream station (e.g., a BS or a UE) andsends a transmission of the data and/or other information to adownstream station (e.g., a UE or a BS). A relay station may also be aUE that relays transmissions for other UEs. In the example shown in FIG.1, a relay station 110 r may communicate with the BS 110 a and a UE 120r in order to facilitate communication between the BS 110 a and the UE120 r. A relay station may also be referred to as a relay BS, a relay,etc.

Wireless communication network 100 may be a heterogeneous network thatincludes BSs of different types, e.g., macro BS, pico BS, femto BS,relays, etc. These different types of BSs may have different transmitpower levels, different coverage areas, and different impact oninterference in the wireless communication network 100. For example,macro BS may have a high transmit power level (e.g., 20 Watts) whereaspico BS, femto BS, and relays may have a lower transmit power level(e.g., 1 Watt).

Wireless communication network 100 may support synchronous orasynchronous operation. For synchronous operation, the BSs may havesimilar frame timing, and transmissions from different BSs may beapproximately aligned in time. For asynchronous operation, the BSs mayhave different frame timing, and transmissions from different BSs maynot be aligned in time. The techniques described herein may be used forboth synchronous and asynchronous operation.

A network controller 130 may couple to a set of BSs and providecoordination and control for these BSs. The network controller 130 maycommunicate with the BSs 110 via a backhaul. The BSs 110 may alsocommunicate with one another (e.g., directly or indirectly) via wirelessor wireline backhaul.

The UEs 120 (e.g., 120 x, 120 y, etc.) may be dispersed throughout thewireless communication network 100, and each UE may be stationary ormobile. A UE may also be referred to as a mobile station, a terminal, anaccess terminal, a subscriber unit, a station, a Customer PremisesEquipment (CPE), a cellular phone, a smart phone, a personal digitalassistant (PDA), a wireless modem, a wireless communication device, ahandheld device, a laptop computer, a cordless phone, a wireless localloop (WLL) station, a tablet computer, a camera, a gaming device, anetbook, a smartbook, an ultrabook, an appliance, a medical device ormedical equipment, a biometric sensor/device, a wearable device such asa smart watch, smart clothing, smart glasses, a smart wrist band, smartjewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainmentdevice (e.g., a music device, a video device, a satellite radio, etc.),a vehicular component or sensor, a smart meter/sensor, industrialmanufacturing equipment, a global positioning system device, or anyother suitable device that is configured to communicate via a wirelessor wired medium. Some UEs may be considered machine-type communication(MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include,for example, robots, drones, remote devices, sensors, meters, monitors,location tags, etc., that may communicate with a BS, another device(e.g., remote device), or some other entity. A wireless node mayprovide, for example, connectivity for or to a network (e.g., a widearea network such as Internet or a cellular network) via a wired orwireless communication link. Some UEs may be consideredInternet-of-Things (IoT) devices, which may be narrowband IoT (NB-IoT)devices.

Certain wireless networks (e.g., LTE) utilize orthogonal frequencydivision multiplexing (OFDM) on the downlink and single-carrierfrequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDMpartition the system bandwidth into multiple (K) orthogonal subcarriers,which are also commonly referred to as tones, bins, etc. Each subcarriermay be modulated with data. In general, modulation symbols are sent inthe frequency domain with OFDM and in the time domain with SC-FDM. Thespacing between adjacent subcarriers may be fixed, and the total numberof subcarriers (K) may be dependent on the system bandwidth. Forexample, the spacing of the subcarriers may be 15 kHz and the minimumresource allocation (called a “resource block” (RB)) may be 12subcarriers (or 180 kHz). Consequently, the nominal Fast FourierTransfer (FFT) size may be equal to 128, 256, 512, 1024 or 2048 forsystem bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz),respectively. The system bandwidth may also be partitioned intosubbands. For example, a subband may cover 1.08 MHz (i.e., 6 resourceblocks), and there may be 1, 2, 4, 8, or 16 subbands for systembandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.

While aspects of the examples described herein may be associated withLTE technologies, aspects of the present disclosure may be applicablewith other wireless communications systems, such as NR.

NR may utilize OFDM with a CP on the uplink and downlink and includesupport for half-duplex operation using TDD. Beamforming may besupported and beam direction may be dynamically configured. MIMOtransmissions with precoding may also be supported. MIMO configurationsin the DL may support up to 8 transmit antennas with multi-layer DLtransmissions up to 8 streams and up to 2 streams per UE. Multi-layertransmissions with up to 2 streams per UE may be supported. Aggregationof multiple cells may be supported with up to 8 serving cells.

In some examples, access to the air interface may be scheduled. Ascheduling entity (e.g., a BS) allocates resources for communicationamong some or all devices and equipment within its service area or cell.The scheduling entity may be responsible for scheduling, assigning,reconfiguring, and releasing resources for one or more subordinateentities. That is, for scheduled communication, subordinate entitiesutilize resources allocated by the scheduling entity. Base stations arenot the only entities that may function as a scheduling entity. In someexamples, a UE may function as a scheduling entity and may scheduleresources for one or more subordinate entities (e.g., one or more otherUEs), and the other UEs may utilize the resources scheduled by the UEfor wireless communication. In some examples, a UE may function as ascheduling entity in a peer-to-peer (P2P) network, and/or in a meshnetwork. In a mesh network example, UEs may communicate directly withone another in addition to communicating with a scheduling entity.

In FIG. 1, a solid line with double arrows indicates desiredtransmissions between a UE and a serving BS, which is a BS designated toserve the UE on the downlink and/or uplink. A finely dashed line withdouble arrows indicates interfering transmissions between a UE and a BS.FIG. 2 illustrates an example logical architecture of a distributedRadio Access Network (RAN) 200, which may be implemented in the wirelesscommunication network 100 illustrated in FIG. 1. A 5G access node 206may include an access node controller (ANC) 202. ANC 202 may be acentral unit (CU) of the distributed RAN 200. The backhaul interface tothe Next Generation Core Network (NG-CN) 204 may terminate at ANC 202.The backhaul interface to neighboring next generation access Nodes(NG-ANs) 210 may terminate at ANC 202. ANC 202 may include one or moreTRPs 208 (e.g., cells, BSs, gNBs, etc.).

The TRPs 208 may be a distributed unit (DU). TRPs 208 may be connectedto a single ANC (e.g., ANC 202) or more than one ANC (not illustrated).For example, for RAN sharing, radio as a service (RaaS), and servicespecific AND deployments, TRPs 208 may be connected to more than oneANC. TRPs 208 may each include one or more antenna ports. TRPs 208 maybe configured to individually (e.g., dynamic selection) or jointly(e.g., joint transmission) serve traffic to a UE.

The logical architecture of distributed RAN 200 may support fronthaulingsolutions across different deployment types. For example, the logicalarchitecture may be based on transmit network capabilities (e.g.,bandwidth, latency, and/or jitter). The logical architecture ofdistributed RAN 200 may share features and/or components with LTE. Forexample, next generation access node (NG-AN) 210 may support dualconnectivity with NR and may share a common fronthaul for LTE and NR.The logical architecture of distributed RAN 200 may enable cooperationbetween and among TRPs 208, for example, within a TRP and/or across TRPsvia ANC 202. An inter-TRP interface may not be used.

Logical functions may be dynamically distributed in the logicalarchitecture of distributed RAN 200. As will be described in more detailwith reference to FIG. 5, the Radio Resource Control (RRC) layer, PacketData Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer,Medium Access Control (MAC) layer, and a Physical (PHY) layers may beadaptably placed at the DU (e.g., TRP 208) or CU (e.g., ANC 202).

FIG. 3 illustrates an example physical architecture of a distributed RAN300, according to aspects of the present disclosure. A centralized corenetwork unit (C-CU) 302 may host core network functions. C-CU 302 may becentrally deployed. C-CU 302 functionality may be offloaded (e.g., toadvanced wireless services (AWS)), in an effort to handle peak capacity.

A centralized RAN unit (C-RU) 304 may host one or more ANC functions.Optionally, the C-RU 304 may host core network functions locally. TheC-RU 304 may have distributed deployment. The C-RU 304 may be close tothe network edge.

A DU 306 may host one or more TRPs (Edge Node (EN), an Edge Unit (EU), aRadio Head (RH), a Smart Radio Head (SRH), or the like). The DU may belocated at edges of the network with radio frequency (RF) functionality.

FIG. 4 illustrates example components of BS 110 and UE 120 (as depictedin FIG. 1), which may be used to implement aspects of the presentdisclosure. For example, antennas 452, processors 466, 458, 464, and/orcontroller/processor 480 of the UE 120 and/or antennas 434, processors420, 430, 438, and/or controller/processor 440 of the BS 110 may be usedto perform the various techniques and methods described herein.

At the BS 110, a transmit processor 420 may receive data from a datasource 412 and control information from a controller/processor 440. Thecontrol information may be for the physical broadcast channel (PBCH),physical control format indicator channel (PCFICH), physical hybrid ARQindicator channel (PHICH), physical downlink control channel (PDCCH),group common PDCCH (GC PDCCH), etc. The data may be for the physicaldownlink shared channel (PDSCH), etc. The processor 420 may process(e.g., encode and symbol map) the data and control information to obtaindata symbols and control symbols, respectively. The processor 420 mayalso generate reference symbols, e.g., for the primary synchronizationsignal (PSS), secondary synchronization signal (SSS), and cell-specificreference signal (CRS). A transmit (TX) multiple-input multiple-output(MIMO) processor 430 may perform spatial processing (e.g., precoding) onthe data symbols, the control symbols, and/or the reference symbols, ifapplicable, and may provide output symbol streams to the modulators(MODs) 432 a through 432 t. Each modulator 432 may process a respectiveoutput symbol stream (e.g., for OFDM, etc.) to obtain an output samplestream. Each modulator may further process (e.g., convert to analog,amplify, filter, and upconvert) the output sample stream to obtain adownlink signal. Downlink signals from modulators 432 a through 432 tmay be transmitted via the antennas 434 a through 434 t, respectively.

At the UE 120, the antennas 452 a through 452 r may receive the downlinksignals from the base station 110 and may provide received signals tothe demodulators (DEMODs) in transceivers 454 a through 454 r,respectively. Each demodulator 454 may condition (e.g., filter, amplify,downconvert, and digitize) a respective received signal to obtain inputsamples. Each demodulator may further process the input samples (e.g.,for OFDM, etc.) to obtain received symbols. A MIMO detector 456 mayobtain received symbols from all the demodulators 454 a through 454 r,perform MIMO detection on the received symbols if applicable, andprovide detected symbols. A receive processor 458 may process (e.g.,demodulate, deinterleave, and decode) the detected symbols, providedecoded data for the UE 120 to a data sink 460, and provide decodedcontrol information to a controller/processor 480.

On the uplink, at UE 120, a transmit processor 464 may receive andprocess data (e.g., for the physical uplink shared channel (PUSCH)) froma data source 462 and control information (e.g., for the physical uplinkcontrol channel (PUCCH) from the controller/processor 480. The transmitprocessor 464 may also generate reference symbols for a reference signal(e.g., for the sounding reference signal (SRS)). The symbols from thetransmit processor 464 may be precoded by a TX MIMO processor 466 ifapplicable, further processed by the demodulators in transceivers 454 athrough 454 r (e.g., for SC-FDM, etc.), and transmitted to the basestation 110. At the BS 110, the uplink signals from the UE 120 may bereceived by the antennas 434, processed by the modulators 432, detectedby a MIMO detector 436 if applicable, and further processed by a receiveprocessor 438 to obtain decoded data and control information sent by theUE 120. The receive processor 438 may provide the decoded data to a datasink 439 and the decoded control information to the controller/processor440.

The controllers/processors 440 and 480 may direct the operation at the BS 110 and the UE 120, respectively. The processor 440 and/or otherprocessors and modules at the BS 110 may perform or direct the executionof processes for the techniques described herein. The memories 442 and482 may store data and program codes for BS 110 and UE 120,respectively. A scheduler 444 may schedule UEs for data transmission onthe downlink and/or uplink.

FIG. 5 illustrates a diagram 500 showing examples for implementing acommunications protocol stack, according to aspects of the presentdisclosure. The illustrated communications protocol stacks may beimplemented by devices operating in a wireless communication system,such as a 5G system (e.g., a system that supports uplink-basedmobility). Diagram 500 illustrates a communications protocol stackincluding a RRC layer 510, a PDCP layer 515, a RLC layer 520, a MAClayer 525, and a PHY layer 530. In various examples, the layers of aprotocol stack may be implemented as separate modules of software,portions of a processor or ASIC, portions of non-collocated devicesconnected by a communications link, or various combinations thereof.Collocated and non-collocated implementations may be used, for example,in a protocol stack for a network access device (e.g., ANs, CUs, and/orDUs) or a UE.

A first option 505-a shows a split implementation of a protocol stack,in which implementation of the protocol stack is split between acentralized network access device (e.g., an ANC 202 in FIG. 2) anddistributed network access device (e.g., DU 208 in FIG. 2). In the firstoption 505-a, an RRC layer 510 and a PDCP layer 515 may be implementedby the central unit, and an RLC layer 520, a MAC layer 525, and a PHYlayer 530 may be implemented by the DU. In various examples the CU andthe DU may be collocated or non-collocated. The first option 505-a maybe useful in a macro cell, micro cell, or pico cell deployment.

A second option 505-b shows a unified implementation of a protocolstack, in which the protocol stack is implemented in a single networkaccess device. In the second option, RRC layer 510, PDCP layer 515, RLClayer 520, MAC layer 525, and PHY layer 530 may each be implemented bythe AN. The second option 505-b may be useful in, for example, a femtocell deployment.

Regardless of whether a network access device implements part or all ofa protocol stack, a UE may implement an entire protocol stack as shownin 505-c (e.g., the RRC layer 510, the PDCP layer 515, the RLC layer520, the MAC layer 525, and the PHY layer 530).

In LTE, the basic transmission time interval (TTI) or packet duration isthe 1 ms subframe. In NR, a subframe is still 1 ms, but the basic TTI isreferred to as a slot. A subframe contains a variable number of slots(e.g., 1, 2, 4, 8, 16, . . . slots) depending on the subcarrier spacing.The NR RB is 12 consecutive frequency subcarriers. NR may support a basesubcarrier spacing of 15 KHz and other subcarrier spacing may be definedwith respect to the base subcarrier spacing, for example, 30 kHz, 60kHz, 120 kHz, 240 kHz, etc. The symbol and slot lengths scale with thesubcarrier spacing. The CP length also depends on the subcarrierspacing.

FIG. 6 is a diagram showing an example of a frame format 600 for NR. Thetransmission timeline for each of the downlink and uplink may bepartitioned into units of radio frames. Each radio frame may have apredetermined duration (e.g., 10 ms) and may be partitioned into 10subframes, each of 1 ms, with indices of 0 through 9. Each subframe mayinclude a variable number of slots depending on the subcarrier spacing.Each slot may include a variable number of symbol periods (e.g., 7 or 14symbols) depending on the subcarrier spacing. The symbol periods in eachslot may be assigned indices. A mini-slot, which may be referred to as asub-slot structure, refers to a transmit time interval having a durationless than a slot (e.g., 2, 3, or 4 symbols).

Each symbol in a slot may indicate a link direction (e.g., DL, UL, orflexible) for data transmission and the link direction for each subframemay be dynamically switched. The link directions may be based on theslot format. Each slot may include DL/UL data as well as DL/UL controlinformation.

In NR, a synchronization signal (SS) block is transmitted. The SS blockincludes a PSS, a SSS, and a two symbol PBCH. The SS block can betransmitted in a fixed slot location, such as the symbols 0-3 as shownin FIG. 6. The PSS and SSS may be used by UEs for cell search andacquisition. The PSS may provide half-frame timing, the SS may providethe CP length and frame timing. The PSS and SSS may provide the cellidentity. The PBCH carries some basic system information, such asdownlink system bandwidth, timing information within radio frame, SSburst set periodicity, system frame number, etc. The SS blocks may beorganized into SS bursts to support beam sweeping. Further systeminformation such as, remaining minimum system information (RMSI), systeminformation blocks (SIBs), other system information (OSI) can betransmitted on a physical downlink shared channel (PDSCH) in certainsubframes. The SS block can be transmitted up to sixty-four times, forexample, with up to sixty-four different beam directions for mmW. The upto sixty-four transmissions of the SS block are referred to as the SSburst set. SS blocks in an SS burst set are transmitted in the samefrequency region, while SS blocks in different SS bursts sets can betransmitted at different frequency locations.

In some circumstances, two or more subordinate entities (e.g., UEs) maycommunicate with each other using sidelink signals. Real-worldapplications of such sidelink communications may include public safety,proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V)communications, Internet-of-Everything (IoE) communications, IoTcommunications, mission-critical mesh, and/or various other suitableapplications. Generally, a sidelink signal may refer to a signalcommunicated from one subordinate entity (e.g., UE1) to anothersubordinate entity (e.g., UE2) without relaying that communicationthrough the scheduling entity (e.g., UE or BS), even though thescheduling entity may be utilized for scheduling and/or controlpurposes. In some examples, the sidelink signals may be communicatedusing a licensed spectrum (unlike wireless local area networks, whichtypically use an unlicensed spectrum).

A UE may operate in various radio resource configurations, including aconfiguration associated with transmitting pilots using a dedicated setof resources (e.g., a radio resource control (RRC) dedicated state,etc.) or a configuration associated with transmitting pilots using acommon set of resources (e.g., an RRC common state, etc.). Whenoperating in the RRC dedicated state, the UE may select a dedicated setof resources for transmitting a pilot signal to a network. Whenoperating in the RRC common state, the UE may select a common set ofresources for transmitting a pilot signal to the network. In eithercase, a pilot signal transmitted by the UE may be received by one ormore network access devices, such as an AN, or a DU, or portionsthereof. Each receiving network access device may be configured toreceive and measure pilot signals transmitted on the common set ofresources, and also receive and measure pilot signals transmitted ondedicated sets of resources allocated to the UEs for which the networkaccess device is a member of a monitoring set of network access devicesfor the UE. One or more of the receiving network access devices, or a CUto which receiving network access device(s) transmit the measurements ofthe pilot signals, may use the measurements to identify serving cellsfor the UEs, or to initiate a change of serving cell for one or more ofthe UEs.

Example UCI Transmission for Overlapping Uplink Resource Assignmentswith Repetition

Aspects of the present disclosure provide apparatus, methods, processingsystems, and computer readable mediums for NR system (e.g., new radioaccess or 5G technology). Certain aspects provide techniques fortransmission of uplink control information (UCI) in NR.

A base station (e.g., such as a BS 110 illustrated in the wirelesscommunication network 100 in FIG. 1) can schedule a user equipment(e.g., such as UE 120 illustrated in the wireless communication network100 in FIG. 1) for uplink transmission. For example, the BS may schedulethe UE for a physical uplink shared channel (PUSCH) transmission and/ora physical uplink control channel (PUCCH) transmission. In certainsystems, such as NR, PUSCH and/or PUCCH can be configured forrepetitions. The PUSCH and/or PUCCH can be associated with a repetitionfactor (e.g., 1, 2, 4, 8) that specifies the number of transmission timeintervals (TTIs), such as slots, in which the transmission is repeated.The slots may be in a single subframe or in different subframes. Thetransmissions may be scheduled on particular orthogonal frequencydivision multiplexed (OFDM) symbols within the slots.

The scheduled transmissions may overlap in some or all of the scheduledslots. Transmitting the overlapping PUSCH and/or PUCCH (e.g.,simultaneously) in the same slot may result in a maximum power reduction(MPR), an increased peak-to-average power ratio (PAPR), powertransitions within a slot, etc. Rules may be applied for transmitting ordropping on the scheduled channels in slots in which the transmissionsoverlap, and/or for piggybacking (i.e., multiplexing) UCI on PUSCH whenthe PUCCH is dropped.

Techniques are desired for rules for which channels to transmit or dropand where to transmit or drop UCI when repetitions are configured forthe PUSCH and/or PUCCH.

Accordingly, aspects of the present disclosure provide techniques andapparatus for UCI transmission for overlapping PUSCH and/or PUCCHresource assignments with repetition.

FIG. 7 is a flow diagram illustrating example operations 700 forwireless communications, in accordance with certain aspects of thepresent disclosure. The operations 700 may be performed by a UE (e.g.,such as one of the UEs 120 illustrated in FIG. 1). Operations 700 may beimplemented as software components that are executed and run on one ormore processors (e.g., processor 480 of FIG. 4). Further, thetransmission and reception of signals by the UE in operations 700 may beenabled, for example, by one or more antennas (e.g., antennas 452 ofFIG. 4). In certain aspects, the transmission and/or reception ofsignals by the UE may be implemented via a bus interface of one or moreprocessors (e.g., processor 480) obtaining and/or outputting signals.

The operations 700 may begin, at 702, by receiving scheduling (e.g., aresource assignment) to transmit on a PUSCH in a first one or more slotsassociated with a first number of repetitions (e.g., a first repetitionfactor) and receiving scheduling to transmit on a PUCCH in a second oneor more slots associated with a second number of repetitions (e.g., asecond repetition factor). The repetition factor may specify the numberof slots on which the associated PUSCH or PUCCH is repeated. Arepetition factor of 1 may indicate no repetition (i.e., only 1 slottransmission). Repetitions may be in consecutive slots or innon-consecutive slots. Repetitions may be in slots in the same subframe,in different subframes, and/or in different frames. For example, someslots may not have a sufficient number of UL symbols to make thetransmission (e.g., the symbols might have been switched to DL by someother signaling) and those slots may be skipped for repetitions.

The scheduled PUSCH and/or PUCCH transmissions overlap in at least oneslot (e.g., in a partially or fully overlapping set of slots and in apartially or fully overlapping set of OFDM symbols within a slot).

At 704, the UE determines to transmit UCI on the PUSCH (e.g., piggyback)and drop the scheduled PUCCH transmission, to transmit the UCI on thePUCCH and drop the scheduled PUSCH transmission, or to drop the UCItransmission for each of the first and second one or more slots. Asdescribed in more detail below, the determination may be based on a ruleor set of rules. The rules may depend on various factors, such as apriority level associated with the transmissions (as shown at optional711 in FIG. 7), the nature of the overlapping transmissions (as shown atoptional 812 in FIG. 7), content of the transmissions, timing of thetransmissions, timing of the resource assignments for the transmissions,etc.

At 706, the UE transmits or drops the UCI (e.g., and the PUSCH andPUCCH) in the first and second one or more slots in accordance with thedetermination.

FIG. 8 is a flow diagram illustrating example operations 800 forwireless communication, in accordance with certain aspects of thepresent disclosure. The operations 800 may be performed by a BS (e.g.,such as a BS 110 in the wireless communication network 100 illustratedin FIG. 1). The operations 800 may be complementary operations by the BSto the operations 700 performed by the UE. Operations 800 may beimplemented as software components that are executed and run on one ormore processors (e.g., processor 440 of FIG. 4). Further, thetransmission and reception of signals by the BS in operations 800 may beenabled, for example, by one or more antennas (e.g., antennas 434 ofFIG. 4). In certain aspects, the transmission and/or reception ofsignals by the BS may be implemented via a bus interface of one or moreprocessors (e.g., processor 440) obtaining and/or outputting signals.

The operations 800 may begin, at 802, by scheduling the UE to transmiton the PUSCH in the first one or more slots associated with the firstnumber of repetitions and to transmit on the PUCCH in the second one ormore slots associated with the second number of repetitions, where thescheduled PUSCH and PUCCH transmissions overlap in at least one slot.

At 804, in the first and second scheduled one or more slots the BSreceives UCI from the UE on the scheduled PUSCH (e.g., piggybacked), butdoes not receive the scheduled PUCCH transmission (e.g., because thePUCCH was dropped by the UE), or the BS receives the UCI on thescheduled PUCCH but does not receive the scheduled PUSCH transmission(e.g., because the PUSCH was dropped by the UE), or the BS may notreceive the UCI (e.g., because the UCI was dropped by the UE).

As mentioned above, the determination by the UE of which channels onwhich to transmit UCI or to drop may be based on a rule or set of rules.The rules may depend on various factors, such as a priority levelassociated with the transmissions, the nature of the overlappingtransmissions, content of the transmissions, timing of thetransmissions, timing of the resource assignments for the transmissions,etc.

The examples rules and factors discussed herein may not be exhaustiveand may not be mutually exclusive. Other suitable rules may be used formaking the determination and the rules may be based on other suitablefactors. Appropriate combinations of rules and factors may be used tomake the determination.

According to certain aspects, the determination is based, at least inpart, on relative priorities of the channels and/or UCI. For example,the determination may be based on a first priority level associated withthe UCI and a second priority level associated with the PUSCH.

A priority level of the PUSCH may be based on the respective prioritylevels of the logical channel(s) associated with (e.g., having bitscarried in) the PUSCH. For example, the PUSCH may be associated withdifferent logical channels for different services, such as for enhancedmobile broadband (eMBB) and ultra-reliable low-latency communications(URLLC). In some examples, the priority level for the PUSCH is thehighest priority level of the associated logical channels. A prioritylevel of the UCI may be based on a priority level, or a highest prioritylevel, of the UCI content (e.g., information). In some examples, apriority of hybrid automatic repeat request (HARD) acknowledgement (ACK)information (e.g., ACK/NACK feedback) is based on the priority level ofthe corresponding physical downlink shared channel (PDSCH) beingacknowledged. In some examples, a priority level of a scheduling request(SR) is based on the priority level of the logical channel associatedwith the SR. If multiple SR resources corresponding to different logicalchannels overlap with the PUSCH resource, the SR included with the PUSCHmay correspond to the one with the highest logical channel priority orthe one with the SR resource that begins earlier.

The UE may be configured with the priority to apply to the channels. Forexample, the UE may be hardwired, the priority may be specified in thewireless standards, and/or the priorities may be signaled to the UE. Insome examples, the priorities may be, in descending order of priority,ACK/NACK information having a highest priority, then schedulingrequests, a first type of channel state information (e.g., periodicCSI), a second type of CSI (e.g., semi-persistent CSI), a third type ofCSI (e.g., periodic CSI), and then PUSCH data having the lowestpriority. In some examples, a different order of priorities can beconfigured. For example, SR could be prioritized over ACK if uplinktraffic is deemed more important than downlink traffic.

According to certain aspects, the determination by the UE of whichchannels on which to transmit UCI or to drop is based, at least in part,on the overlap of the scheduled transmissions. For example, thedetermination may be based on whether the transmissions are overlappingintra-slot and/or inter-slot.

For intra-slot overlapping, the determination is based on whether theoverlapping transmissions are scheduled for transmission on OFDM symbolswithin a slot that are fully overlapping (e.g., the same set of OFDMsymbols in the slot are scheduled for PUSCH and PUCCH) or partiallyoverlapping (e.g., some OFDM symbols are scheduled for overlappingtransmissions, other OFDM symbols are not). If the transmissions in theslot are only on a partially overlapping set of OFDM symbols, then thedetermination may be further based on which assignment starts earlier orlater and/or which assignment ends earlier or later. In some examples,the transmissions may be scheduled for different OFDM symbols fordifferent slots; thus, the intra-slot overlapping may be different fordifferent slots.

For inter-slot overlapping, the determination may be based on whetherthe scheduled slots are fully overlapping (e.g., the same set of slotsare scheduled for transmissions) or partially overlapping (e.g., someslots overlap, other slots do not). If the scheduled transmissions areonly in a partially overlapping set of slots, then the determination maybe further based on which assignment starts earlier or later and/orwhich assignment ends earlier or later.

According to certain aspects, the determination is based, at least inpart, on a type of information associated with the UCI (e.g., content ofthe UCI).

According to certain aspects, the determination is based, at least inpart, on the resource assignments scheduling the overlappingtransmissions. For example, the determination may be based on whetherthe resource assignments are semi-static or dynamic and/or a time whenthe resource assignments are received.

According to certain aspects, the rule(s) may be determined/defined foroverlap in one slot (e.g., without repetition). The determination forthe 1-slot rule may be based on any of the factors discussed above, or acombination of those factors and/or other factors. For full overlap, thesame rule(s) may be extended to repetition slots. For example, in eachof the scheduled slots, the same rule/determination can be applied fortransmission/dropping of PUSCH/PUCCH/UCI. For partial overlap, thedetermination for the 1-slot rule may be applied to only the overlappingslots—and not to the other slots. In some examples, one channel (e.g.,PUSCH or PUCCH) may be dropped. The channel may be dropped on everyslot, dropped only on overlapping slots, or may be dropped starting atthe first overlapping slot and remaining slots. The channel to bedropped may be based on a priority level of the channel, timing of theassignments, when the assignments were known (e.g., receivedsemi-statically or dynamically), or a combination of these.

In some examples, for partial overlap, the received/configuredassignments scheduling the overlapping transmissions can be adjusted tocreate (e.g., enforce or achieve) additional overlap or full overlap.One or more of the assignments may be implicitly extended to reduce oreliminate the number of non-overlapping slots. For example, if one ofthe assignments is semi-static, then the overlap can be predicted assoon as the other assignment (e.g., a dynamic assignment for the otherchannel) is received. Based on the predicted overlap, the semi-staticassignment can be extended to overlap with the dynamic assignment. Inthis case, the rule/determination for one slot can be used for all ofthe overlapping slots.

In some examples, other adjustments may be made to the assignments toallow improved processing. For example, if one of the assignments is fora single slot, the 1-slot rules may be applied on that slot only. It maybe advantageous to shift that overlapping slot to the beginning or tothe end of the other multi-slot assignment to obtain a contiguous set ofslot repetitions with the same structure or to improve the UE processingtimeline. In an illustrative example, when a 1-slot PUSCH overlaps withan N-slot PUCCH, the 1-slot PUSCH can be moved to the first or last ofthe N slots, the UCI is piggybacked on the 1-slot PUSCH, and transmittedon the remaining N-1 slots. Whether the PUSCH is moved to the beginningor the end of the assignment may be decided by (e.g., determined basedon) other factors such as, for example, based on the nature of theoverlap within the slot (e.g., which of the two resource assignments,PUSCH or PUCCH, has the earlier starting or ending OFDM symbol).Shifting an assignment to a later slot may also improve the processingtimeline. For example, if a 1-slot PUCCH overlaps the first slot of a2-slot PUSCH and the PUSCH begins earlier than the PUCCH, then if UCI ispiggybacked on the first slot, the UCI should be available earlier thanif there was no overlapping PUSCH. Instead, the UCI could be piggybackedon the second slot of PUSCH. This could be interpreted as following thepiggyback rule within the overlapping slot after first delaying thePUCCH assignment by 1 slot.

If the payload is not ready, a stale/previous payload may be used (e.g.,an old/previous CSI), or the assignment may not be extended, or one ofthe transmissions may be dropped. Generally, as long as full extensioncan be honored with sufficient advance notice for both PUCCH ACK andPUSCH, for example based on the k1 timeline (i.e., the gap between PDSCHand the corresponding ACK) and the k2 timeline (i.e., the gap betweenPUSCH assignment grant and PUSCH transmission), then full extension canbe allowed. In an illustrative example, a dynamically scheduled 1-slot(i.e., configured repetition factor of 1) ACK overlaps the third slot ofa 4-slot (i.e., configured repetition factor of 4) semi-persistent PUSCHassignment. The 1-slot ACK assignment may be extended to cover all slotsof the 4-slot PUSCH assignment, provided the ACK assignment was knownsufficiently in advance of the first slot of the 4-slot PUSCH assignment(e.g., based on the minimum k1 value). If the ACK assignment is notknown sufficiently in advance to extend to all slots of 4-slot PUSCHassignment, then the ACK is not extended or may be extended only toslots where it is sufficient. In another illustrative example, both theACK assignment and the PUSCH assignment are dynamically scheduled. Ifthe dynamic PUSCH assignment was known before the dynamic ACK assignmentwas known (e.g., the DCI for the PUSCH was received first), then theapproach from the previous illustrative example can be followed.

According to certain aspects, certain overlaps may be disallowed. Forexample, the gNB may not schedule (e.g., avoid scheduling) certainoverlaps and the UE may not expect the gNB to schedule disallowedoverlaps.

According to certain aspects, the UE may reject one or more assignments(e.g., uplink grants) scheduling PUSCH and PUCCH transmissions in one ormore overlapping slots. In some examples, if the grant for one channelis dynamic and the grant for another channel is semi-static, the UE mayreject the dynamic grant. In some examples, if the grant for bothchannels is dynamic, the UE may accept whichever grant is received firstand reject the later received grant, or the UE may reject the grant thatis received first and reject accept the more recent grant. In someexamples, if the grant for one channel is dynamic and the grant foranother channel is received at the same, or if both grants are dynamic,the UE may accept the grant for PUCCH and reject the grant for PUSCH. Insome examples, if the grant for PUSCH is much smaller (e.g., lowerpayload capacity) than the grant for PUCCH, the UE may reject the PUSCHgrant and not piggyback UCI on PUSCH.

In some examples, the rules may be a function of the timing of theassignments. For example, the relative priorities of PUCCH and PUSCH maybe a function of the assignment durations for the PUCCH and PUSCH. Ashorter duration transmission may be associated with lower latencyrequirement and, thus, with higher priority than a longer durationtransmission. Some examples are the short PUCCH (e.g., of 1 or 2 OFDMsymbol duration) and non-slot PUSCH (e.g., type-B which may also bereferred to as a mini-slot PUSCH transmission), which may be prioritizedhigher than the long PUCCH (e.g., of 4 or more OFDM symbol duration) andslot-based PUSCH (e.g., type-A transmission), respectively.

When both PUCCH and PUSCH are of the same priority (e.g., short PUCCHand non-slot PUSCH, or long PUCCH and slot based PUSCH), the determinedrules to be applied may be different from those when the PUCCH and PUSCHare of different priority. For example, when PUSCH and PUCCH have thesame priority, the transmission that begins later in time may bedropped, and when PUSCH and PUCCH have different priorities, even if thehigher priority transmission begins later, the earlier transmission maybe dropped or suspended after partial transmission in order to allow thehigher priority transmission to proceed. The suspended transmission maybe disallowed from resuming within the slot in which the suspensionbegan, even after the higher priority transmission has completed,because resuming that transmission may not be possible while maintainingphase coherence with the original portion of the transmission that wassent prior to suspension. When slot repetition is configured, thesuspended transmission may be disallowed form resuming in subsequentrepeated slots as well. Alternatively, since each repeated slot has itsown demodulation reference signal (DMRS), the lower prioritytransmission may be allowed to resume in subsequent repeated slots.

Although the techniques discussed herein refer to examples of PUSCH andPUCCH, the techniques described herein can be extended to the cases ofmore than two transmission resources with partial or complete overlapbetween different subsets of the resources. For example, an N-slot PUCCHmay overlap two successive PUSCH transmissions. The UCI may bepiggybacked on one or both of the PUSCH transmissions. In some examples,the PUSCH transmission or transmissions to piggyback the UCI may bedetermined based on the nature of the symbol-level overlap within theoverlapping slots, or based on which of the PUSCH transmissions is oflonger duration. In some examples, the PUCCH may also be transmitted onthe slots without overlapping PUSCH. The techniques discussed herein canalso be extended to the case where the more than two transmissionresources are contained in the same slot. For example, a 1-slot PUCCHmay overlap two successive contiguous or non-contiguous PUSCHtransmissions within the same slot (e.g., mini-slot transmissions). TheUCI may be piggybacked on one or both of the PUSCH.

According to certain aspects, the transmit beam to use for thetransmissions may be determined. In some examples, rules for determiningthe transmit beam or beams for PUCCH and PUSCH transmissions can bedetermined according to the techniques described herein. In someexamples, in each slot it can first be determined whether thetransmission is made on PUCCH or on PUSCH (i.e., according to the singleslot rule for that slot), and then the beam for the correspondingtransmission in that slot is determined. This may result in differentbeams for different slots, for example, if UCI is piggybacked only onthe overlapping slots. Thus, in some examples, the transmission andtransmit beam are determined for the first slot of the transmission, andthen the determined beam for the first slot is used for all subsequenttransmissions in the subsequent slots. Using the same beam canfacilitate phase-coherence assumption in the pilot signals (such as DMRSand phase tracking reference signals (PTRS)) across the transmissions,which can enable a joint channel and phase-noise estimation across theslots.

The techniques for beam determination described herein may be appliedeven for a 1-slot PUCCH assignment overlapping a 1-slot PUSCH. In someexamples, the UE may use either the PUCCH beam or the PUSCH beam, andthe UE may determine the beam based on various factors, such as whetherthe transmission occurs on PUCCH or PUSCH, the nature of the UCI, etc.In some examples, the UE may use the PUSCH beam regardless whether thePUSCH carries only SCH data, only piggybacked UCI, or both SCH data andUCI.

The techniques for beam determination described herein may also beapplied when there is no overlap between PUSCH and PUCCH assignments. Insome examples, the UE reuses the beam determined in the first slot inall later slots. In some examples, the beam is updated based on anappropriate beam determination rule. For example, the UE may determinethe transmit beam for PUSCH based on a beam indicator in the PUSCHgrant, or based on a beam of a recent PUCCH or PDCCH resource if thebeam indicator is absent. The recent PUCCH or PDCCH resource may be thesame for all repeated PUSCH slots, or may update for successive slots ifmore recent PUCCH or PDCCH resources occur during the slot repetitions.The beam associated with the recent PUCCH or PDCCH resource may beupdated, for example, based on radio resource control (RRC) or mediumaccess control (MAC) control element (CE) signaling, during the slotrepetitions. The updates may be included or excluded for the purpose ofbeam determination for repeated PUSCH slots.

FIG. 9 illustrates a communications device 900 that may include variouscomponents (e.g., corresponding to means-plus-function components)configured to perform operations for the techniques disclosed herein,such as the operations illustrated in FIG. 7. The communications device900 includes a processing system 902 coupled to a transceiver 908. Thetransceiver 908 is configured to transmit and receive signals for thecommunications device 900 via an antenna 910, such as the varioussignals as described herein. The processing system 902 may be configuredto perform processing functions for the communications device 900,including processing signals received and/or to be transmitted by thecommunications device 900.

The processing system 902 includes a processor 904 coupled to acomputer-readable medium/memory 912 via a bus 906. In certain aspects,the computer-readable medium/memory 912 is configured to storeinstructions (e.g., computer-executable code) that when executed by theprocessor 904, cause the processor 904 to perform the operationsillustrated in FIG. 7, or other operations for performing the varioustechniques discussed herein for UCI transmission with overlapping uplinkassignments. In certain aspects, computer-readable medium/memory 912stores code 914 for receiving scheduling for PUSCH and PUCCH, forexample code for receiving scheduling to transmit on the PUSCH in afirst one or more slots associated with a first number of repetitionsand scheduling to transmit on the PUCCH in a second one or more slotsassociated with a second number of repetitions, wherein the scheduledPUSCH and PUCCH transmissions overlap in at least one slot, inaccordance with aspects of the present disclosure; code 914 fordetermining to transmit or drop UCI, PUCCH, and PUSCH, for example codefor determining to transmit UCI on the PUSCH and drop the scheduledPUCCH transmission, to transmit the UCI on the PUCCH and drop thescheduled PUSCH transmission, or to drop the UCI transmission for eachof the first and second one or more slots, in accordance with aspects ofthe present disclosure; and code 916 for transmitting or dropping UCIbased on the determination, in accordance with aspects of the presentdisclosure. In certain aspects, the processor 904 has circuitryconfigured to implement the code stored in the computer-readablemedium/memory 912. The processor 904 includes circuitry 920 forreceiving scheduling for PUSCH and PUCCH; circuitry 922 for determiningto transmit or drop UCI, PUCCH, and PUSCH; and circuitry 924 fortransmitting or dropping UCI based on the determination.

FIG. 10 illustrates a communications device 1000 that may includevarious components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as the operations illustrated in FIG. 8. Thecommunications device 1000 includes a processing system 1002 coupled toa transceiver 1008. The transceiver 1008 is configured to transmit andreceive signals for the communications device 1000 via an antenna 1010,such as the various signals as described herein. The processing system1002 may be configured to perform processing functions for thecommunications device 1000, including processing signals received and/orto be transmitted by the communications device 1000.

The processing system 1002 includes a processor 1004 coupled to acomputer-readable medium/memory 1012 via a bus 1006. In certain aspects,the computer-readable medium/memory 1012 is configured to storeinstructions (e.g., computer-executable code) that when executed by theprocessor 1004, cause the processor 1004 to perform the operationsillustrated in FIG. 8, or other operations for performing the varioustechniques discussed herein for UCI transmission with overlapping uplinkassignments. In certain aspects, computer-readable medium/memory 1012stores code 1014 for scheduling a UE to transmit PUSCH and PUCCH, forexample code for scheduling the UE to transmit on the PUSCH in a firstone or more slots associated with a first number of repetitions andscheduling the UE to transmit on the PUCCH in a second one or more slotsassociated with a second number of repetitions, wherein the scheduledPUSCH and PUCCH transmissions overlap in at least one slot, inaccordance with aspects of the present disclosure; and code 1016 forreceiving or not receiving UCI, PUSCH, and PUCCH from the UE, such ascode for receiving UCI from the UE on the scheduled PUSCH, but does notreceiving the scheduled PUCCH transmission, receiving the UCI on thescheduled PUCCH but not receiving the scheduled PUSCH transmission, ornot receiving the UCI, in accordance with aspects of the presentdisclosure. In certain aspects, the processor 1004 has circuitryconfigured to implement the code stored in the computer-readablemedium/memory 1012. The processor 1004 includes circuitry 1018 forscheduling a UE to transmit PUSCH and PUCCH; and circuitry 1020 forreceiving or not receiving UCI, PUSCH, and PUCCH from the UE.

The methods disclosed herein comprise one or more steps or actions forachieving the methods. The method steps and/or actions may beinterchanged with one another without departing from the scope of theclaims. In other words, unless a specific order of steps or actions isspecified, the order and/or use of specific steps and/or actions may bemodified without departing from the scope of the claims.

As used herein, a phrase referring to “at least one of” a list of itemsrefers to any combination of those items, including single members. Asan example, “at least one of: a, b, or c” is intended to cover a, b, c,a-b, a-c, b-c, and a-b-c, as well as any combination with multiples ofthe same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b,b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

As used herein, the term “determining” encompasses a wide variety ofactions. For example, “determining” may include calculating, computing,processing, deriving, investigating, looking up (e.g., looking up in atable, a database or another data structure), ascertaining and the like.Also, “determining” may include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” may include resolving, selecting, choosing, establishingand the like.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language of the claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. All structural andfunctional equivalents to the elements of the various aspects describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and are intended to be encompassed by the claims. Moreover,nothing disclosed herein is intended to be dedicated to the publicregardless of whether such disclosure is explicitly recited in theclaims. No claim element is to be construed under the provisions of 35U.S.C. § 112(f) unless the element is expressly recited using the phrase“means for” or, in the case of a method claim, the element is recitedusing the phrase “step for.”

The various operations of methods described above may be performed byany suitable means capable of performing the corresponding functions.The means may include various hardware and/or software component(s)and/or module(s), including, but not limited to a circuit, anapplication specific integrated circuit (ASIC), or processor. Generally,where there are operations illustrated in figures, those operations mayhave corresponding counterpart means-plus-function components withsimilar numbering.

The various illustrative logical blocks, modules and circuits describedin connection with the present disclosure may be implemented orperformed with a general purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or other programmable logic device (PLD),discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any commercially available processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

If implemented in hardware, an example hardware configuration maycomprise a processing system in a wireless node. The processing systemmay be implemented with a bus architecture. The bus may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system and the overall design constraints.The bus may link together various circuits including a processor,machine-readable media, and a bus interface. The bus interface may beused to connect a network adapter, among other things, to the processingsystem via the bus. The network adapter may be used to implement thesignal processing functions of the PHY layer. In the case of a userterminal 120 (see FIG. 1), a user interface (e.g., keypad, display,mouse, joystick, etc.) may also be connected to the bus. The bus mayalso link various other circuits such as timing sources, peripherals,voltage regulators, power management circuits, and the like, which arewell known in the art, and therefore, will not be described any further.The processor may be implemented with one or more general-purpose and/orspecial-purpose processors. Examples include microprocessors,microcontrollers, DSP processors, and other circuitry that can executesoftware. Those skilled in the art will recognize how best to implementthe described functionality for the processing system depending on theparticular application and the overall design constraints imposed on theoverall system.

If implemented in software, the functions may be stored or transmittedover as one or more instructions or code on a computer readable medium.Software shall be construed broadly to mean instructions, data, or anycombination thereof, whether referred to as software, firmware,middleware, microcode, hardware description language, or otherwise.Computer-readable media include both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. The processor may beresponsible for managing the bus and general processing, including theexecution of software modules stored on the machine-readable storagemedia. A computer-readable storage medium may be coupled to a processorsuch that the processor can read information from, and write informationto, the storage medium. In the alternative, the storage medium may beintegral to the processor. By way of example, the machine-readable mediamay include a transmission line, a carrier wave modulated by data,and/or a computer readable storage medium with instructions storedthereon separate from the wireless node, all of which may be accessed bythe processor through the bus interface. Alternatively, or in addition,the machine-readable media, or any portion thereof, may be integratedinto the processor, such as the case may be with cache and/or generalregister files. Examples of machine-readable storage media may include,by way of example, RAM (Random Access Memory), flash memory, ROM (ReadOnly Memory), PROM (Programmable Read-Only Memory), EPROM (ErasableProgrammable Read-Only Memory), EEPROM (Electrically ErasableProgrammable Read-Only Memory), registers, magnetic disks, opticaldisks, hard drives, or any other suitable storage medium, or anycombination thereof. The machine-readable media may be embodied in acomputer-program product.

A software module may comprise a single instruction, or manyinstructions, and may be distributed over several different codesegments, among different programs, and across multiple storage media.The computer-readable media may comprise a number of software modules.The software modules include instructions that, when executed by anapparatus such as a processor, cause the processing system to performvarious functions. The software modules may include a transmissionmodule and a receiving module. Each software module may reside in asingle storage device or be distributed across multiple storage devices.By way of example, a software module may be loaded into RAM from a harddrive when a triggering event occurs. During execution of the softwaremodule, the processor may load some of the instructions into cache toincrease access speed. One or more cache lines may then be loaded into ageneral register file for execution by the processor. When referring tothe functionality of a software module below, it will be understood thatsuch functionality is implemented by the processor when executinginstructions from that software module.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, server, or otherremote source using a coaxial cable, fiber optic cable, twisted pair,digital subscriber line (DSL), or wireless technologies such as infrared(IR), radio, and microwave, then the coaxial cable, fiber optic cable,twisted pair, DSL, or wireless technologies such as infrared, radio, andmicrowave are included in the definition of medium. Disk and disc, asused herein, include compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Thus, in some aspects computer-readable media maycomprise non-transitory computer-readable media (e.g., tangible media).In addition, for other aspects computer-readable media may comprisetransitory computer-readable media (e.g., a signal). Combinations of theabove should also be included within the scope of computer-readablemedia.

Thus, certain aspects may comprise a computer program product forperforming the operations presented herein. For example, such a computerprogram product may comprise a computer-readable medium havinginstructions stored (and/or encoded) thereon, the instructions beingexecutable by one or more processors to perform the operations describedherein.

Further, it should be appreciated that modules and/or other appropriatemeans for performing the methods and techniques described herein can bedownloaded and/or otherwise obtained by a user terminal and/or basestation as applicable. For example, such a device can be coupled to aserver to facilitate the transfer of means for performing the methodsdescribed herein. Alternatively, various methods described herein can beprovided via storage means (e.g., RAM, ROM, a physical storage mediumsuch as a compact disc (CD) or floppy disk, etc.), such that a userterminal and/or base station can obtain the various methods uponcoupling or providing the storage means to the device. Moreover, anyother suitable technique for providing the methods and techniquesdescribed herein to a device can be utilized.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the methods and apparatus described above without departingfrom the scope of the claims.

What is claimed is:
 1. A method for wireless communications by a userequipment (UE), comprising: scheduling a physical uplink shared channel(PUSCH) transmission in a first one or more slots associated with afirst number of repetitions; scheduling a physical uplink controlchannel (PUCCH) transmission in a second one or more slots associatedwith a second number of repetitions, wherein the PUSCH transmission andthe PUCCH transmission overlap in at least one slot; determining thatthere is a sufficient number of symbols available to transmit uplinkcontrol information (UCI) in the second one or more slots; and based onthe determining that there is a sufficient number of symbols available:transmitting the UCI on the PUCCH, and dropping the PUSCH transmissionin only the at least one overlapping slot.
 2. The method of claim 1,further comprising determining to transmit the UCI on the PUCCH and dropthe PUSCH transmission in only the at least one overlapping slot basedon a first priority level associated with the UCI and a second prioritylevel associated with the PUSCH.
 3. The method of claim 1, furthercomprising determining to transmit the UCI on the PUCCH and drop thePUSCH transmission in only the at least one overlapping slot based onpriority levels of a type of information associated with the UCI,wherein the priority levels comprise, in descending order of priority,ACK/NACK information, scheduling request (SR), a first type of channelstate information (CSI), and a second type of CSI.
 4. The method ofclaim 1, further comprising determining to transmit the UCI on the PUCCHand drop the PUSCH transmission in only the at least one overlappingslot based on a radio resource control (RRC) configuration.
 5. Themethod of claim 1, further comprising determining to transmit the UCI onthe PUCCH and drop the PUSCH transmission in only the at least oneoverlapping slot based on whether the PUCCH transmission or the PUSCHtransmission is scheduled to be transmitted earlier than the other. 6.The method of claim 1, further comprising determining to transmit theUCI on the PUCCH and drop the PUSCH transmission in only the at leastone overlapping slot based on a time a resource assignment for the PUCCHtransmissions is received and a time that a resource assignment for thePUSCH transmission is received.
 7. The method of claim 1, furthercomprising determining to transmit the UCI on the PUCCH and drop thePUSCH transmission in only the at least one overlapping slot accordingto a single-slot rule for transmitting UCI.
 8. The method of claim 7,further comprising determining a beam to use for transmitting the UCI inthe at least one overlapping slot according to the single-slot rule. 9.The method of claim 1, wherein the second number of repetitions isgreater than
 1. 10. The method of claim 1, further comprisingdetermining to transmit the UCI on the PUCCH and drop the PUSCHtransmission in only the at least one overlapping slot based on a typeof service the UE is scheduled to transmit on the PUSCH.
 11. The methodof claim 10, wherein the type of service comprises enhanced mobilebroadband (eMBB) service or ultra-reliable low-latency communication(URLLC) service.
 12. An apparatus for wireless communications,comprising: at least one processor; and a memory coupled to the at leastone processor, the memory comprising code executable by the at least oneprocessor to cause the apparatus to: schedule a physical uplink sharedchannel (PUSCH) transmission in a first one or more slots associatedwith a first number of repetitions; schedule a physical uplink controlchannel (PUCCH) transmission in a second one or more slots associatedwith a second number of repetitions, wherein the PUSCH transmission andthe PUCCH transmission overlap in at least one slot; determine thatthere is a sufficient number of symbols available to transmit uplinkcontrol information (UCI) in the second one or more slots; and based onthe determining that there is a sufficient number of symbols available:transmit the UCI on the PUCCH, and drop the PUSCH transmission in onlythe at least one overlapping slot.
 13. The apparatus of claim 12,wherein the memory further comprises code executable by the at least oneprocessor to cause the apparatus to determine to transmit the UCI on thePUCCH and drop the PUSCH transmission in only the at least oneoverlapping slot based on a first priority level associated with the UCIand a second priority level associated with the PUSCH.
 14. The apparatusof claim 12, wherein the memory further comprises code executable by theat least one processor to cause the apparatus to determine to transmitthe UCI on the PUCCH and drop the PUSCH transmission in only the atleast one overlapping slot based on priority levels of a type ofinformation associated with the UCI, wherein the priority levelscomprise, in descending order of priority, ACK/NACK information,scheduling request (SR), a first type of channel state information(CSI), and a second type of CSI.
 15. The apparatus of claim 12, whereinthe memory further comprises code executable by the at least oneprocessor to cause the apparatus to determine to transmit the UCI on thePUCCH and drop the PUSCH transmission in only the at least oneoverlapping slot based on a radio resource control (RRC) configuration.16. The apparatus of claim 12, wherein the memory further comprises codeexecutable by the at least one processor to cause the apparatus todetermine to transmit the UCI on the PUCCH and drop the PUSCHtransmission in only the at least one overlapping slot based on whetherthe PUCCH transmission or the PUSCH transmission is scheduled to betransmitted earlier than the other.
 17. The apparatus of claim 12,wherein the memory further comprises code executable by the at least oneprocessor to cause the apparatus to determine to transmit the UCI on thePUCCH and drop the PUSCH transmission in only the at least oneoverlapping slot based on a time a resource assignment for the PUCCHtransmissions is received and a time that a resource assignment for thePUSCH transmission is received.
 18. The apparatus of claim 12, whereinthe memory further comprises code executable by the at least oneprocessor to cause the apparatus to determine to transmit the UCI on thePUCCH and drop the PUSCH transmission in only the at least oneoverlapping slot according to a single-slot rule for transmitting UCI.19. The apparatus of claim 12, wherein the memory further comprises codeexecutable by the at least one processor to cause the apparatus todetermine a beam to use for transmitting the UCI in the at least oneoverlapping slot according to a single-slot rule.
 20. The apparatus ofclaim 12, wherein the second number of repetitions is greater than 1.21. The apparatus of claim 12, wherein the memory further comprises codeexecutable by the at least one processor to cause the apparatus todetermine to transmit the UCI on the PUCCH and drop the PUSCHtransmission in only the at least one overlapping slot based on a typeof service the apparatus is scheduled to transmit on the PUSCH.
 22. Theapparatus of claim 21, wherein the type of service comprises enhancedmobile broadband (eMBB) service or ultra-reliable low-latencycommunication (URLLC) service.
 23. An apparatus for wirelesscommunication, comprising: means for scheduling a physical uplink sharedchannel (PUSCH) transmission in a first one or more slots associatedwith a first number of repetitions; means for scheduling a physicaluplink control channel (PUCCH) transmission in a second one or moreslots associated with a second number of repetitions, wherein the PUSCHtransmission and the PUCCH transmissions overlap in at least one slot;means for determining that there is a sufficient number of symbolsavailable to transmit uplink control information (UCI) in the second oneor more slots; means for transmitting the UCI on the PUCCH based on thedetermining that there is a sufficient number of symbols available; andmeans for dropping the PUSCH transmission in only the at least oneoverlapping slot based on the determining that there is a sufficientnumber of symbols available.
 24. The apparatus of claim 23, furthercomprising means for determining to transmit the UCI on the PUCCH anddrop the PUSCH transmission in only the at least one overlapping slotbased on a first priority level associated with the UCI and a secondpriority level associated with the PUSCH.
 25. The apparatus of claim 23,further comprising means for determining to transmit the UCI on thePUCCH and drop the PUSCH transmission in only the at least oneoverlapping slot based on priority levels of a type of informationassociated with the UCI, wherein the priority levels comprise, indescending order of priority, ACK/NACK information, scheduling request(SR), a first type of channel state information (CSI), and a second typeof CSI.
 26. The apparatus of claim 23, further comprising means fordetermining to transmit the UCI on the PUCCH and drop the PUSCHtransmission in only the at least one overlapping slot based on a radioresource control (RRC) configuration.
 27. A non-transitory computerreadable medium having computer executable code stored thereon forwireless communications, comprising: code for scheduling a physicaluplink shared channel (PUSCH) transmission in a first one or more slotsassociated with a first number of repetitions; code for scheduling aphysical uplink control channel (PUCCH) transmission in a second one ormore slots associated with a second number of repetitions, wherein thePUSCH transmission and the PUCCH transmissions overlap in at least oneslot; code for determining that there is a sufficient number of symbolsavailable to transmit uplink control information (UCI) in the second oneor more slots; code for transmitting the UCI on the PUCCH based on thedetermination that there is a sufficient number of symbols available;and code for dropping the PUSCH transmission in only the at least oneoverlapping slot based on the determination that there is a sufficientnumber of symbols available.
 28. The non-transitory computer readablemedium of claim 27, further comprising code for determining to transmitthe UCI on the PUCCH and drop the PUSCH transmission in only the atleast one overlapping slot based on a first priority level associatedwith the UCI and a second priority level associated with the PUSCH. 29.The non-transitory computer readable medium of claim 27, furthercomprising code for determining to transmit the UCI on the PUCCH anddrop the PUSCH transmission in only the at least one overlapping slotbased on priority levels of a type of information associated with theUCI, wherein the priority levels comprise, in descending order ofpriority, ACK/NACK information, scheduling request (SR), a first type ofchannel state information (CSI), and a second type of CSI.
 30. Thenon-transitory computer readable medium of claim 27, further comprisingcode for determining to transmit the UCI on the PUCCH and drop the PUSCHtransmission in only the at least one overlapping slot based on a radioresource control (RRC) configuration.
 31. A method for wirelesscommunications by a user equipment (UE), comprising: receivingscheduling for a physical uplink shared channel (PUSCH) transmission ina first one or more slots associated with a first number of repetitions;receiving scheduling for a physical uplink control channel (PUCCH)transmission in a second one or more slots associated with a secondnumber of repetitions, wherein the PUSCH transmission and the PUCCHtransmission are scheduled to overlap in at least one slot, and whereinthe scheduled PUCCH transmission in the second one or more slotsincludes a sufficient number of symbols available to transmit uplinkcontrol information (UCI); transmitting the UCI on the PUCCH; andtransmitting the PUSCH transmission in the first one or more slotsexcluding the at least one overlapping slot.
 32. The method of claim 31,wherein the second number of repetitions is greater than 1.